Messages
hsc is able to produce lots of different warnings and
errors when parsing html-files. The messages alway look the same:
"file" (line#, colum#), class and message-id, message
with
file input file that caused message; file names surrounded by
"[" and "]" indicate pseudo-filenames like macros.
line#, position in input file that caused error
colum#
class one of Note, Warning, Error or Fatal error
message message text
Message Classes
Note is a message only for the
users information. It can be suppressed using IGNORE
.
Bad style informs the user that
his altough legal HTML-code includes constructs that indicate a bad style.
It can be suppressed using IGNORE
.
Portability problem informs the
user that his altough legal HTML-code includes constructs can lead to problems
on old or buggy browsers.IGNORE
.
Warning tells you that your source
includes some problematic parts, that can lead to problems with several
browsers.
It can be suppressed using IGNORE
.
Error indicates that there is something
wrong with your HTML-source. No output is written.
Fatal error tells you that something
terrible has happened and there is no way to continue the conversion.
No output is written.
Note: I've already started to collect the messages, but
this list is not yet complete.
-
error1:
- Undocumented.
-
error1:
- Undocumented.
-
fatal3:
unexpected end of file
-
There are still characters to be read from input, but the file
already ends. Usualy, hsc tells you what it still expects to come.
-
error4:
- Undocumented.
-
error5:
- Undocumented.
-
fatal6:
can not open file for input
-
An input file could not been opened. A more detailed message that tells
you why is displayed, too.
-
error7:
- Undocumented.
-
error8:
- Undocumented.
-
error9:
- Undocumented.
-
style10:
"click here" syndrome detected
-
A keyword defined with the global attribute
__CLICK_HERE__
has been found within the text inside an anchor specification.
Ok, now again in english: you used some term like "Click here" inside
the text describing a link. This is very clumsy and should be avoided;
see Composing
Good HTML for details.
-
error11:
unknown tag <tag>
-
You refered to an unknown tag or macro.
-
error12:
tag <tag> occured too often
-
A tag that is expected to occure only once appeared at least twice.
Remove all unneccessary occurences of the tag.
-
warning13:
unmatched end-tag <tag>
-
You called a end-tag without using the corresponding start-tag
before.
-
warning14:
illegal end-tag nesting
- Undocumented.
A end-tag appeard where a different end-tag was expected to
appear before. Example: instead of
<B><I>bold and italic</B></I>
you should write
<B><I>bold and italic</I></B>
-
warning15:
required tag <tag> missing
-
A tag that is required for every document is missing.
-
warning16:
end-tag <tag> missing
-
You called an start-tag, but didn't end it. Insert the required
end-tag.
-
error17:
- Undocumented.
-
warning18:
unknown entity
-
You used an entity, that hsc doesn't know. This can happen if you
made a typo, or the entity has not been defined within
hsc.prefs.
-
error19:
- Undocumented.
-
error20:
reference to unknown attribute
-
You referered to an attribute that doesn't exist at all.
-
warning21:
path to URI not found: file
-
A tag points to a local resource that doesn't exist.
-
warning22:
argument without quote
-
You passed a value to an attribute, but did not embed it into single
or double quotes. This can lead to problems with older browsers.
-
error23:
empty reference to attribute attrib
-
An attribute referes to an attribute that has been defined, but no
value has been set for. Usually, you try to refer to an attribute
inside a macro, that no value has been passed to within the call
of the macro.
-
error24:
- Undocumented.
-
style25:
<BLINK>
sucks
-
Some browser support the non-HTML-tag
<BLINK>
. It is used
to make text blinking, which annoys many users. Additionally, most
of them don't know how to configure their browser that it doesn't
blink, so you really should avoid it.
-
error26:
- Undocumented.
-
error27:
- Undocumented.
-
error28:
- Undocumented.
-
error29:
- Undocumented.
-
error30:
unmatched ">"
-
A "greater than" sign appeared inside the text. You should write
"
>
" instead. This can also happen, if you made
an error calling a tag, and hsc's parser couln't recover.
-
error31:
- Undocumented.
-
error32:
- Undocumented.
-
error33:
- Undocumented.
-
error34:
- Undocumented.
-
error35:
unknown value value for enumerator attribute attrib
-
You tried to set an enumerator to a value it doesn't support.
-
error36:
- Undocumented.
-
warning37:
tag <tag> is obsolete
-
The tag was defined within some old HTML-version, but should
not be used any more (eg.
<LISTING>
).
-
warning38:
tag <tag> is only used by jerks
-
This tag is no legal HTML-tag and is only supportet by special
browsers.
-
error39:
- Undocumented.
-
error40:
- Undocumented.
-
error41:
- Undocumented.
-
error42:
- Undocumented.
-
error43:
unknown attribute option option
-
You defined a new attribute, but used an
option that is unknown.
-
error44:
required attribute attrib missing
-
An attribute that is required has not been set within the call
of a tag or macro.
-
error45:
- Undocumented.
-
note46:
replaced char by entity
-
Informs you that a special character (non-7-bit-ASCII) has been replaced
by it's corresponding entity.
-
error47:
- Undocumented.
-
error48:
- Undocumented.
-
error49:
- Undocumented.
-
error50:
- Undocumented.
-
note51:
quote found inside text
-
A quote has been found inside the text. This doesn't indicate
any problems, I think, but can someone tell me why they invented
"
"
"? Probably only to be used inside strings,
I think..
-
error52:
- Undocumented.
-
error53:
- Undocumented.
-
error54:
- Undocumented.
-
error55:
- Undocumented.
-
error56:
- Undocumented.
-
error57:
- Undocumented.
-
error58:
- Undocumented.
-
error59:
- Undocumented.
-
error60:
tag <tag> must be inside tag <tag>
-
Before you are allowed to use the first tag, the second tag has to
occure before. Example:
<INPUT>
may only occure
inside <FORM>
.
-
error61:
tag <tag> not allowed within tag <tag>
-
A tag occures inside another tag that doesn't allowe this. For example,
you can't recursively use
<A>
inside <A>
.
-
error62:
no attributes allowed for end-tags
-
You tried to pass values to a end-tag or macro. If you need an attribute
for a end-macro only, you still have to define and pass it within the
opening macro.
-
warning63:
redefinance of attribute attrib
-
You redefined an alredy existing attribute. If this occures during
the definition of a new macro, you just tried to give two arguments the
same name.
-
error64:
- Undocumented.
-
error65:
- Undocumented.
-
error66:
illegal end-tag
-
You tried to use a simple tag as a container.
-
error67:
- Undocumented.
-
error68:
- Undocumented.
-
error69:
- Undocumented.
-
error70:
- Undocumented.
-
error71:
- Undocumented.
Thomas Aglassinger (
agi@giga.or.at
), 15-May-1996